Synchronizing history data across a virtualized web browser

ABSTRACT

Approaches for synchronizing history data across a virtualized web browser. When a user instructs a virtualized web browser, executing on a host operating system, to display a web page, a host module executing on the host operating system may instruct a guest module executing within a particular virtual machine to retrieve the web page. The host module may provide to the guest module history data for the virtualized web browser. History data describes browsing history for the virtualized web browser, either in the current instance or for previous instances. The guest module performs operations in accordance with the history data. When the host module receives the screen data content from the guest module, the host module instructs the virtualized web browser to display the web page using the screen data content.

RELATED APPLICATION DATA

This application is related to U.S. non-provisional patent applicationSer. No. 13/115,354 (the “'354 patent”), filed May 25, 2011, which has apriority date of May 28, 2010, entitled “Approaches for Securing anInternet Endpoint using Fine-Grained Operating System Virtualization,”the contents of which are hereby incorporated by reference for allpurposes as if fully set forth herein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/223,091, filed Aug. 31, 2011, entitled “Approaches forAutomated Management of Virtual Machines for Running Untrusted CodeSafely,” the contents of which are hereby incorporated by reference forall purposes as if fully set forth herein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/302,123, filed Nov. 22, 2011, entitled “Approaches forEfficient Physical to Virtual Disk Conversion,” invented by Gaurav Bangaet al., the contents of which are hereby incorporated by reference forall purposes as if fully set forth herein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/419,345, filed Mar. 13, 2012, entitled “Seamless Managementof Untrusted Data Using Virtual Machines,” invented by Gaurav Banga etal., the contents of which are hereby incorporated by reference for allpurposes as if fully set forth herein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/358,434, filed Jan. 25, 2012, entitled “Approaches forProtecting Sensitive Data Within a Guest Operating System,” invented byGianni Tedesco et al., the contents of which are hereby incorporated byreference for all purposes as if fully set forth herein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/468,742, filed May 10, 2012, entitled “Reducing MemoryRequirements for Guest Operating Systems,” invented by Kris Uchronski etal., the contents of which are hereby incorporated by reference for allpurposes as if fully set forth herein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/468,781, filed May 10, 2012, entitled “Preparing a VirtualMachine for Template Creation,” invented by Kris Uchronski et al., thecontents of which are hereby incorporated by reference for all purposesas if fully set forth herein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/468,805, filed May 10, 2012, entitled “Managing the EvictionProcess,” invented by Kris Uchronski et al., the contents of which arehereby incorporated by reference for all purposes as if fully set forthherein.

This application is related to U.S. non-provisional patent applicationSer. No. 13/468,843, filed May 10, 2012, entitled “Mitigating VirtualMachine Memory Eviction Using Mapping Tables,” invented by KrisUchronski et al., the contents of which are hereby incorporated byreference for all purposes as if fully set forth herein.

FIELD OF THE INVENTION

Embodiments of the invention relate to synchronizing history data of avirtualized web browser.

BACKGROUND

Ensuring the security of computer networks and network connected devicesis one of the grand challenges facing us today. The current state ofaffairs is very problematic, as our cyber-security infrastructure isroutinely subverted by cyber criminals, resulting in great economicloss, invasion of privacy, and loss of productivity.

Certain web browsers have attempted to provide a level of security byisolating downloaded code. However, present approaches for doing so arefairly primitive in their ability to deal with the full gamut ofsecurity issues that arise during the course of a typical user's webexperience. For example, the sandboxing capability of certain versionsof Google's web browser does not address safety issues arising fromdownloaded browser plugins and various types of native executables, andtherefore, possesses a vulnerability to a zero day exploit attack thatvia Adobe Flash or Microsoft Word.

Web browser vendors rely upon monetizing the web browsing habits oftheir users within their own business processes and with their industrypartners. This monetization relies, at least in part, on data aboutusers' browsing habits which is stored in the web cookies that are setand later provided to web servers during the course of web sessions.Companies such as Google and Microsoft have a great interest in learningas much as possible about a person's browsing habits and typicallyarrange the default privacy settings of web browsers to be advantageousto them, but less than optimal from a security and privacy standpoint.The default privacy settings causes web browsers to transfer largeamounts of sensitive information from users' machines to Internetrelated businesses, such as Google, Microsoft, Apple, etc., therebyallowing such businesses to better monetize their customer base byoffering appropriate products and services and serving targeted ads.These same settings, however, can be leveraged by malicious parties toexploit security vulnerabilities. While all web browsers provide somelevel of control to the sophisticated user to tune his or her webbrowser privacy settings, the vast majority of users never change thedefault settings.

According to some current approaches for enhancing the security of acomputer, the computer runs multiple independent operating systems usingmultiple virtual machines (VMs) within the computer. Multiple virtualmachines may be created using a hypervisor, such as from VMware of PaloAlto, Calif. or Virtual PC, available from Microsoft Corporation ofRedmond, Wash. When client virtualization is used to achieve improvedsecurity, different VMs are used to run different types or classes ofapplications. For example, an operating system in one VM may bededicated for accessing the corporate network that the user may be partof and running corporate applications (local and web). Another operatingsystem in a second VM might be used by the user to run his or herpersonal programs and store personal documents. Finally, a differentoperating system in a third VM may be used for general web browsing onthe wider Internet and running native executables that may have beendownloaded from the Internet. An example of such a solution isXenClient, which is made by Citrix Systems of Ft Lauderdale, Fla.

This use of classical client virtualization suffers from severaldrawbacks. One drawback is that there is too much management overheadfor the end-user. The end-user has the onus of making the decision as towhat VM to use for each activity. Any mistake, intentional oraccidental, may subvert the integrity of the system. While manysafeguards can be added as a layer on top of the core virtualizationtechnology to help prevent the user from making mistakes, this has notyet been demonstrated to work in a practical and robust fashion.

Another drawback is that any VM that is used for general web browsing isjust as vulnerable to a security problem as any monolithic systemrunning a single VM while accessing web sites on the general Internet.Therefore, it is quite likely that any VM dedicated to web browsingdescribed in the arrangement above will be subverted by malwareeventually. Any subsequent activities in that VM, then, will becompromised.

For these and other reasons, client virtualization has not been usedwidely to improve the security of computer systems.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings and inwhich like reference numerals refer to similar elements and in which:

FIG. 1 is a block diagram of system according to one embodiment of theinvention;

FIG. 2 is a flowchart illustrating the steps of retrieving a web pageusing a virtualized web browser according to an embodiment of theinvention;

FIG. 3 is a block diagram illustrating which virtual machines in anillustrative system are responsible for retrieving and renderingportions of a single requested web page according to an embodiment ofthe invention;

FIG. 4 is an illustration of injecting state data into a virtual machineaccording to an embodiment of the invention;

FIG. 5 is an illustration of an application downloading a file to anintermediate location according to an embodiment of the invention;

FIG. 6 is an illustration of an application uploading a file to anintermediate location according to an embodiment of the invention; and

FIG. 7 is a block diagram that illustrates a computer system upon whichan embodiment of the invention may be implemented.

DETAILED DESCRIPTION OF EMBODIMENTS

Approaches for synchronizing history data of a virtualized web browserare presented herein. In the following description, for the purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the embodiments of the invention describedherein. It will be apparent, however, that the embodiments of theinvention described herein may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form or discussed at a high level in order to avoidunnecessarily obscuring teachings of embodiments of the invention.

Virtualized Web Browser

Embodiments of the invention are directed towards a virtualized webbrowser. A virtualized web browser refers to a plurality of componentsthat cooperate to provide a secure web browsing experience. Acharacteristic of a virtualized web browser is that a portion of thecomponents implementing the virtualized web browser resides in the hostwhile another portion of the components implementing the virtualized webbrowser resides in one or more virtual machines. While the portion ofthe virtualized web browser that resides in the host is responsible fordisplaying content, that portion need not retrieve the displayed contentfrom across the network. Instead, the content displayed by a virtualizedweb browser is typically retrieved by components in one or more virtualmachines, although the component(s) of the virtualized web browserresiding in the host may retrieve and render content if desired.

A virtualized web browser presents the same user experience as atraditional (or “native”) web browser. A person using a virtualized webbrowser may, in fact, not even realize that they aren't using atraditional web browser. Therefore, a user of a virtualized web browserneed not alter their usage patterns and may use a virtualized webbrowser in the same way as a traditional web browser.

As used herein, the term “web browser” will be used to refer to bothtraditional web browsers and virtualized web browsers. When specificreference is made to traditional web browsers (i.e., those web browserswhich are not virtualized web browsers), the term “traditional webbrowsers” or “native web browsers” will be used herein.

The types of operations that are typically performed on a web browserinclude, without limitation, browsing to various web sites, enteringinformation and logging into web pages, navigating back and forthbetween visited web pages, uploading and downloading content through aweb page, and saving and using bookmarks. To support such activity, webbrowsers maintain temporary and persistent state information to ensuresuch operations are properly performed.

The desire to ensure that a virtualized web browser offers the same userexperience as a traditional web browser requires that virtualized webbrowsers manage the temporary and persistent state information necessaryto perform expected web browser operations across the underlyingmicro-virtualization environment in which these operations areperformed. Many approaches will be presented herein for synchronizingresources of a virtualized web browser so that the virtualized webbrowser provides a familiar user experience. Prior to doing so however,a more detailed description of how a virtualized web browser of anembodiment operates will be presented.

Anatomy of a Virtualized Web Browser

To better appreciate how a virtualized web browser operates, considerFIG. 1, which is a block diagram of system 100 according to oneembodiment of the invention. System 100 includes a virtualized webbrowser that has components that are implemented on the host as well ason different virtual machines. FIG. 1 depicts host 110 and virtualmachines 120A, 120B, . . . 120N. Host 110 corresponds to the hostoperating system installed upon a device. Host 110 may be embodied by awide variety of operating systems, either presently available orsubsequently developed.

In an embodiment (not depicted in FIG. 1), the functional componentsresiding in host 110 may instead reside in a persistently maintainedvirtual machine.

Virtual machines 120A, 120B, . . . 120N each represent any type ofvirtual machine. In an embodiment, virtual machines 120A, 120B, . . .120N may each correspond to an Untrusted Code Virtual Machine (UCVM)discussed in the '354 patent. While FIG. 1 only specifically identifiesthree virtual machines, namely virtual machines 120A, 120B, and 120N,the graphical notations of FIG. 1 are meant to convey that embodimentsof the invention may employ any number of virtual machines. Moreover,during the normal course of operation, virtual machines may beperiodically instantiated or destroyed, and so the particular number ofvirtual machines within system 100 will always be changing during normaloperation.

Virtual machines 120A, 120B, . . . 120N may reside on the same physicalmachine as host 110, but they need not. In fact, one or more of virtualmachines 120A, 120B, . . . 120N may reside on a different physicalmachine than on which host 110 resides and may communicate with host 110over a network. For example, host 110 may be implemented on a cellphone, laptop computer, tablet computer, PC, or other device orcomputer, and virtual machines 120A, 120B, . . . 120N may be implementedon one or more separate physical machines located over a network. Tofacilitate the retrieval of web content, virtual machines 120A, 120B, .. . 120N may have a network connection. Note that the particular networksettings and network configuration of virtual machines 120A, 120B, . . .120N may be different and specifically tailored to suit the activityassigned thereto.

In a virtualized web browser of an embodiment, different virtualmachines may be used to perform user initiated actions such asretrieving requested content from the Internet. Each of virtual machines120A, 120B, . . . 120N is completely isolated from each other and fromhost 110. As shall be explained below in greater detail, thedetermination of which virtual machine a particular action should beperformed in may be based on policy, as reasons will be discussed forwanting to perform certain actions together in the same virtual machineas well as reasons for wanting to perform various actions in separatevirtual machines.

As shown in FIG. 1, host 110 comprises web browser 112 while virtualmachines 120A, 120B, . . . 120N each comprise web browsers 122A, 122B, .. . 122N respectively. For clarity, web browsers 122A, 122B, . . . 122Nshall be termed VM web browsers to signify that the web browsers executewithin a virtual machine in system 100. By the same token, web browser112 shall be termed host web browser 112 to signify that it executeswithin host 110.

A virtualized web browser of an embodiment is comprised of host webbrowser 112, one or more VM web browsers, such as VM web browsers 122A,122B, and 122N, host module 114, and one or more guest modules, such asguest modules 124A, 124B, and 124N. Host module 114 and guest modules124A, 124B, and 124N are components which assist in synchronizingresources of the virtualized web browser.

VM web browsers 122A, 122B, and 122N and other applications that are runon behalf of the virtualized web browser in each virtual machine storeand update the state of a user's web browser session. However, sinceeach VM web browser is running in an isolated virtual machine, the statechanges made to the web browser session made by a particular virtualmachine are local to that virtual machine. This provides completeisolation between various user actions, which assists in promotingsecurity; however, isolating virtual machines from one anotherfrustrates certain interfaces and behavior of a web browser that theuser expects.

Therefore, host module 114 and guest modules 124A, 124B, and 124Ncooperate to share information about certain changes made to the webbrowser session and synchronize resources when appropriate. The guestmodule within each virtual machine tracks the resources that arerequested and updated by the VM web browser within that virtual machine.For example, guest module 124A within virtual machine 120A tracks theresources that are requested and updated by web browser 122A. Hostmodule 114 coordinates resource synchronization between host 110 andvirtual machines 120A, 120B, . . . 120N. Host module 114 and the guestmodules within each virtual machine communicate over securecommunication channels that are not accessible to possible insecure coderunning in virtual machines 120A, 120B, . . . 120N or in host 110.

Host module 114 and guest modules 124A, 124B, and 124N provide aninterface to host web browser 112 so that information about the activityin virtual machines 120A, 120B, . . . 120N is shared as needed andreflected in the user experience provided by the virtualized webbrowser. As a result of the activity of host module 114 and guestmodules 124A, 124B, . . . 124N, the user is not responsible forcoordinating the activity of the underlying micro-virtualization of thevirtualized web browser.

To illustrate the role played by host module 114 and guest modules 124A,124B, . . . 124N, consider that the VM web browser in each virtualmachine maintains its own list of history entries reflecting where thatparticular VM web browser navigated. However, the user expects that anynavigations previously performed by him to show up in the historyentries of the virtualized web browser regardless of which particular VMweb browser was involved in the navigation. Therefore, operationsinvolving a user's past navigation history should reflect the browsinghistory of the user regardless of which particular virtual machine wasresponsible for retrieving the web pages. Host module 114 and guestmodules 124A, 124B, . . . 124N help ensure that relevant informationabout the user's browsing activity is shared appropriately between host110 and virtual machines 120A, 120B, . . . 120N so that browsing historybehaves as expected.

Another illustration of how host module 114 and guest modules 124A,124B, . . . 124N synchronize resources of a virtualized web browser maybe shown by their coordinated support for the use of APIs from popularweb sites such as Facebook and Google on third-party web sites. When onevisits a third party web site that is integrated with Facebook, the webbrowser ideally uses secure mechanisms to show content related to yourFacebook account on the third party web site. For example, a news website can show stories that your friends from Facebook “liked” on thatnews web site. These types of web page features typically use cookies orweb protocols such as OAuth. Cookies are resources that are exchangedbetween the web browser and web sites being visited by the user. If VMweb browser 122A executing in virtual machine 120A and the web sitebeing browsed by VM web browser 122A exchange cookies, then the cookieswill likely be needed in host 110 (and potentially in other virtualmachines as explained below) to ensure that the display of the web pageproperly integrates with Facebook. Therefore, as shall be explained inmore detail below, host module 114 and guest modules 124A, 124B, . . .124N make sure that each virtual machine has the cookies necessary sothat the VM web browser executing therein can properly display andrender any web page retrieved by that VM web browser.

Operation of a Virtualized Web Browser

Embodiments of the invention seamlessly synchronize resources of avirtualized web browser to present a completely native browserexperience to the end user. A wide variety of resources may becoordinated between host 110 and virtual machines 120A, 120B, . . . 120Nincluding without limitation: URLs, screen data for all or at least aportion of a web page retrieved by VM web browser, user input (such askeyboard and mouse actions) directed against a web page displayed by aweb browser, cookies, navigation history, bookmarks, configurationsettings for the web browser, cache files of various types, DOM storage,and files saved and uploaded. Any type of data that indicates a changein state in the user's web browsing experience (“state data”) may besynchronized as appropriate between host 110 and virtual machines 120A,120B, . . . 120N according to embodiments.

Prior to discussing in detail how these types of resources aresynchronized, it will be helpful to understand how a virtualized webbrowser retrieves and displays a requested web page. FIG. 2 is aflowchart illustrating the steps of retrieving a web page using avirtualized web browser according to an embodiment of the invention.

In step 210, a user instructs a virtualized web browser to display a webpage. As previously explained, the user may not know that the webbrowser he or she is using is a virtualized web browser, as thevirtualized web browser will exhibit the appearance and behavior of atraditional web browser. However, in all actuality, when a userinteracts with a virtualized web browser, the user is actually directlyinteracting with host web browser 112 executing in host 110.

The user actions taken with respect to host web browser 112 areidentified by host module 114 in cooperation with host web browser 112.Embodiments may inform host module 114 of the user actions taken withrespect to host web browser 112 using a variety of different techniques.Different types of web browsers and/or host operating system may providedifferent options for informing host module 114 of user actions directedagainst host web browser 112, and embodiments of the invention mayemploy any appropriate manner to do so. Non-limiting, illustrativemechanisms for enabling communication between host web browser 112 andhost module 114 include APIs, callbacks, and web browser plug-ins. Torecite one specific example, in an embodiment where host web browser 112is a version of Microsoft Internet Explorer, then Browser Helper Objects(BHO) may be used to inform module 114 of user actions directed againsthost web browser 112. As another example, host web browser 112 may beaugmented with a plug-in that causes host module 114 to be informed ofany user input submitted to host web browser 112.

Once host module 114 identifies a user action directed against host webbrowser 112, host module 114 either performs the request action itselfor forwards notice of the requested action to an appropriate virtualmachine within system 100 for processing. Host module 114 may consultpolicy data to determine whether the user action should be processedwithin host 110 or within a particular virtual machine.

To provide a concrete example, assume the user action is a request todisplay a web page. Further assume that host module 114, in consultationwith policy data, determines that virtual machine 120A is theappropriate virtual machine responsible for retrieving that web page.

In an embodiment, the particular virtual machine selected by host module114 to process any user input or perform any requested user action willpossess characteristics appropriate for the type of activity involved indoing so. In this example, virtual machine 120A should be configured topossess appropriate characteristics for retrieving the type of web pagebeing requested. If the requested web page is a web page on an internalcorporate intranet site, then virtual machine 120A should haveappropriately tailored configuration settings to do so in a manner thataddresses any security concerns. Similarly, if the requested web page isa web page associated with the user's personal bank or other suchfinancial institution, then virtual machine 120A may have a differentset of configuration settings to address the particular type of activityand level of risk involved

Virtual machine 120A need not be instantiated at the time host module114 determines that virtual machine 120A should retrieve the web page,as virtual machine 120A may be instantiated on-the-fly. Host module 110may instruct a hypervisor to create a particular virtual machine using atemplate that causes the particular virtual machine to havecharacteristics chosen for particular task at hand, namely retrieving aparticular web page in this example. Any instantiated virtual machinewill comprise a guest module and may comprise a VM web browser.Additional description of how virtual machines may be implementedon-the-fly with specifically tailored characteristics is described inthe previously mentioned '354 patent.

To inform virtual machine 120A to retrieve the requested web page, hostmodule 114 communicates an instruction to guest module 124A withinvirtual machine 120A to retrieve the requested web page. If VM webbrowser 122A is not instantiated at the time guest module 124A receivesthe instruction to retrieve the requested web page, then guest module124A instantiates VM web browser 122A at that time.

In step 220, guest module 124A instructs VM web browser 122A to retrievethe requested web page. In response, VM web browser 122A retrieves therequested web page and renders the web page. Note that as VM web browser122A is executing within virtual machine 120A, the rendering of therequested web page by VM web browser 122A will not cause the renderedweb page to be visually displayed to the user by VM web browser 122A,but instead, the retrieved web page is merely interpreted without beingshown upon a connected display device.

Instead, host web browser 112 is responsible for displaying theretrieved web page on a connected physical display device. To make thisso, the visual appearance of the web page rendered by VM web browser122A is shown as the web page displayed by host web browser 112. Inother words, the content that was to be shown by VM web browser 122A isinstead shown by host web browser 112.

There are many ways in which the screen of a VM web browser may bedisplayed to the user by host web browser 112. One way involves guestmodule 124A generating or obtaining a graphical representation (termed“screen data”) of the rendered web page. Screen data is a graphicaldepiction of at least a portion of the appearance of the web page.Screen data may represent the visual presentation of the entire web pageor, as is performed by some embodiments, only a portion of the web page.For example, an uninterpreted web page may be represented as an HTMLfile, whereas screen data for that web page may be an image file, suchas a file in a JPEG, TIF, PNG, or GIF format. Screen data may beembodied using any type of format for defining how to display content,such as a graphical representation.

In an embodiment, after guest module 124A obtains screen data for therequested web page, guest module 124A sends the screen data for therequested web page to host module 114.

In another embodiment, once screen data is generated for the requestedweb page, host module 114 retrieves the screen data for the requestedweb page from virtual machine 120A. For example, host module 114 mayretrieve the contents from a predetermined location in memory at whichthe screen data is to be stored.

In an embodiment, other data besides screen data may be obtained by hostmodule 114 in step 220. If guest module 124A retrieves a file or graphicin virtual machine 120A, then the graphic or file may be made availableto host module 114. After host module 114 possesses screen data for therequested web page, processing proceeds to step 230.

In step 230, the virtualized web browser processes the data received instep 220 and displays the requested web page. In an embodiment, step 230is performed by host module 114 instructing host web browser 112 todisplay the requested web page using the screen data received from guestmodule 124A. After doing so, the user may physically view the requestedpage upon a display device, as the visual representation of the web pagemay be displayed on a physical display device by host web browser 114.

Note that host web browser 112 may display the requested web page usingthe screen data with or without any visual indicators that identify thatthe requested web page, or any portion thereof, was not retrieved withinhost 110 or by host web browser 112. If the use of visual indicators isdesired, a specifically-colored border or a window decoration of aspecial color may be used to denote the host windows or tabs that arebeing rendered in an untrusted virtual machine.

Using Multiple Virtual Machines to Retrieve a Single Requested Web Page

The description of FIG. 2 was presented in terms of a retrieving arequested web page using a single web browser executing on a singlevirtual machine. However, this need not be the case in all embodiments,as other embodiments may employ multiple virtual machines to retrievedifferent portions of a single requested web page. In such anembodiment, host web browser 112 would display the requested web page bydisplaying the assembled portions of screen data received from the twoor more virtual machines involved in retrieving the different portionsof the web page.

To further illustrate such an embodiment, consider FIG. 3, which is ablock diagram illustrating which virtual machines in system 100 areresponsible for retrieving and rendering portions of a single requestedweb page according to an embodiment of the invention. FIG. 3 depicts webpage 310 that comprises two bounded areas of content 312 and 314.Bounded areas of content 312 and 314 may be identified using a HTMLconstruct called an “iFrame.” The iFrame HTML tag is supported by allmajor web browsers and is a way to demarcate different portions of a webpage. Within an iFrame, content may originate from a different sourcethan the web page in which it resides. In other words, web page 310,content within iFrame 312, and content within iFrame 314 may eachoriginate from a different source on the Internet.

When host module 114 receives a request to display a web page, hostmodule 114 may instruct multiple virtual machines to return screen datafor certain portions of the requested web page. For example, as depictedin FIG. 3, host module 114 may instruct virtual machine 120A to retrievescreen data for the content web page 310 without any content for iFrame312 or iFrame 314. Also in this example, host module 114 may instructvirtual machine 120B to retrieve screen data for the content associatedwith iFrame 312 and may instruct virtual machine 120N to retrieve screendata for the content associated with iFrame 314. The determination ofwhich virtual machine should retrieve screen data for which portion of arequested web page may be made based on policy, as explained in moredetail in a later section.

When host module 114 receives screen data from two or more guestmodules, host module 114 assembles the graphical images represented bythe sets of screen data and instructs host web browser 112 to displaythe assembled web page. In this way, the web page depicted in FIG. 3 maybe shown to the user without the user being informed that content withiniFrame 312 and content within iFrame 314 were retrieved in a differentvirtual machine than web page 310.

It may be advantageous to retrieve different portions of a web page fromdifferent virtual machines for security purposes. Content containedwithin an iFrame may contain malicious code. It is common foradvertisements and the like to be included within an iFrame.Advertisements and the like may be served by a third party service. As aresult, it is difficult for the operator of a web site to monitorcontent embedded within a web page of their web site for malicious code.By retrieving the content associated with an iFrame in a separatevirtual machine, any malicious code that attempts to access unauthorizedresources will be unable to access other portions of the web page, letalone access to sensitive resources outside of the virtual machine inwhich it executes.

Communication Between the Host Module and the Guest Module During aBrowsing Session

The steps of FIG. 2 describe how the display of a single requested webpage may be performed using a virtualized web browser. During the courseof a normal web browsing session, a user will, naturally, interact witha displayed web page, either by clicking a link on the web page,entering and submitting text via a text box, and other more complexclick and type interactions. Since different virtual machines may beresponsible for retrieving different web pages, or even differentportions of the same web page, any interaction of the user with aparticular portion of a web page should be handled by the appropriatevirtual machine. To do so, host module 114 and one or more guest moduleswill communicate with each other to support a user's interaction with adisplayed web page.

When a user selects a link on web page, clicks a button, submitscharacter data entered via the keyboard, and the like, host module 114is notified that a user is submitting user input relative to aparticular location on a web page. Host module 114 identifies theportion of a displayed web page to which the user input is directed. Forexample, host module 114 may identify a particular iFrame associatedwith the submitted character data or a particular link that wasselected. In certain embodiments, the host module 114 also identifieswhere the position of a mouse cursor or any other input, such as inputfrom a light pen, a finger on a display, and the like, relative to theweb page. In this way, host module 114 may identify where the mousepointer is relative to the web page to facilitate the performance of amouse hover operation or any other such operation that requires thelocation of the mouse pointer or input mechanism relative to the webpage.

Host module 114 identifies, based on policy and results of prioroperation of the system, the specific virtual machine responsible forthe portion displayed web page to which the user input was directed.Host module 114 then notifies the guest module within the identifiedvirtual machine of the user input. For example, if host module 114determines that virtual machine 120B is responsible for a web page, thenhost module forwards the user input to guest module 124B for processing.

Once guest module 124B receives the user input, guest module 124B willinstruct VM web browser 122B to act on the user input by performing theaction associated with the user input. For example, if the user inputidentifies a particular location on a web page over which the userclicked a mouse button, then VM web browser 122B will navigate the mousepointer to the same location, perform a mouse click operation, andprocess the results. Note that VM web browser 122B will be displayingthe same web page as host web browser 114, and so the user input may beprocessed against the web page displayed by host web browser 114similarly as if host web browser 114 was actually processing the userinput. Once VM web browser 122B has processed the user input (such as,for example, obtaining a requested web page from a remote location inresponse to the user's mouse click), guest module 124B either sendsscreen data for the resulting appearance of the content displayed by VMweb browser 122B to host module 114, or host module 114 retrieves suchscreen data directly from virtual machine 120B, so that host module 114may instruct host web browser 112 to display the screen data to theuser.

Guest module 124B may send a request to host module 124B for anyinformation about the user's web browsing session that is pertinent tothe processing of the user input. If in this example guest module 124Brequires one or more resources from host module 114 to properly processthe user input, then guest module 124B may contact host module 114 toobtain such information. For example, if, in order to properly display aweb page, guest module 124B determines that a particular cookie isneeded, then guest module 124B may obtain the cookie by issuing arequest for the cookie to host module 114.

If the user clicks a link on the displayed web page, guest module 124Bmay send a request to host module 124B to determine if guest module 124Bcan process a subsequent browsing action. If host module 114 allows thisaction, guest module 124B will instruct VM web browser 122B to retrievethe web page indicated by the selected link. On the other hand, if hostmodule 114 denies guest module 124B permission to continue processingthe web processing requests, host module 114 will instruct anothervirtual machine to retrieve the web content identified by the selectedlink. The decision of the host module 114 on whether to allow guestmodule 124B permission to continue processing browsing requests will bemade based on policy data.

Persistently Storing Data and Injecting State Data

Generally, absent special considerations, virtual machines 120A, 120B, .. . 120N are not intended to be persisted ad infinitum. While one ormore of virtual machines 120A, 120B, . . . 120N may be persistentlystored in certain cases, more commonly such virtual machines will bedestroyed or de-allocated when they are no longer required. Thus, thetypical use case of virtual machines 120A, 120B, . . . 120N is toinstantiate them as needed and de-allocate them when their use isconcluded. Consequently, data stored within one of virtual machines120A, 120B, . . . 120N may not be persisted.

As a result, in an embodiment, when a guest module determines that datawithin the virtual machine should be persistently stored, the guestmodule sends a request to host module 114 to persistently store the datawithin host 114. To persistently store data describing state changesmade to the web browsing session (“state data”) at the virtual machine120A, guest module 124A may send a request to persistently store thestate data. Upon receipt of the request, host module 114 stores the datapersistently on host 110. Host module 114 may persistently store data athost 110 at state data storage 130. State data storage 130 may beimplemented by any mechanism capable of storing data, such as a databaseor a file system.

In some embodiments, certain state data may be persisted by updatinghost web browser 112. For example, if the state data which guest module124A is requesting host module 114 to persistently store is aconfiguration setting change to the virtualized web browser, a change tothe user's bookmarks, or a cookie, then such changes may be stored byupdating host web browser 112. Host web browser 112 will thereafterpersist such state changes.

Alternately, rather than persistently storing state data at host 110,data may be persistently stored in a virtual machine that is persisted.In such an embodiment, a guest module may communicate with an entity ina virtual machine to store state data within the virtual machine. Thisembodiment may be useful if it is desired to separate state data fromhost 110. For example, if there is a possibility of a malicious programresiding in the host, by persistently storing the state data in avirtual machine, the malicious program will be unable to inspect thestate data, thereby rendering the state data private and secure. In suchan embodiment, rather than state data storage 130 residing in host 110as depicted in FIG. 1, state data storage 130 will reside in a virtualmachine, such as one of virtual machines 120A, 120B, . . . 120N, whichis configured to be persisted.

The guest module running in each virtual machine has explicit and fullvisibility into the activity occurring within the virtual machine. Theguest module can decide, based on and within the limits of policiescontained within policy data, when the guest module should sendresources or state data to host 110 to assist in servicing activityperformed by the VM web browser. When a VM web browser within a virtualmachine decides to update or save new resources, the guest module withinthat virtual machine may determine, based on the policies within thepolicy data, to send the information back to host module 114. Hostmodule 114 may decide to either update or add to the data stored instate data store 130 using the information sent by the guest module.Host module 114 may also determine to send updates to any currentlyrunning virtual machines that are performing various other navigationsor other browser actions based on policy settings and/or knowledge ofwhat is the activity happening in each of the virtual machines. Thisresource coordination may also make use of the knowledge of what all thevirtual machines are doing with applications and resources other thanthe virtualized web browser.

It will, on occasion, be necessary to inform a virtual machine aboutactivities performed in a web browsing session that occurred outside ofthat virtual machine. To do so, state data for a web browsing session is“injected” into that virtual machine. FIG. 4 is an illustration thatwill be referenced in a discussion of injecting state data into avirtual machine according to an embodiment of the invention. Initially,with reference to FIG. 4, assume that VM web browser 122A is instructedto perform an action by guest module 124A that causes VM web browser122A to change the state of the web browsing session of the user. Guestmodule 124A will be cognizant of any change in the web browsing state asguest module 124A monitors the activity performed by VM web browser122A.

After guest module 124A determines that a state change in the webbrowsing session for the user has occurred in virtual machine 120A,guest module 124A consults policy data to determine whether such changeshould be persisted within system 100. The policy data that is consultedby guest module 124A in this regard may be implemented in a variety ofways. The policy data may reside within guest module 124A or may resideelsewhere, such as a persisted virtual machine dedicated to storingpolicy data. Policy data refers to data that defines one or morepolicies that are used to shape the behavior of one or more componentsof the virtualized web browser. Policy data will be described in greaterdetail below.

Alternately, guest module 124A may be implemented such that guest module124A causes any state data describing a local change in the state of theweb browsing session to be automatically sent to host module 114 ratherthan doing so based on a consultation with policy data. In such anembodiment, host module 114 may be designed to consult policy data todetermine how to process any state data received from a guest module insuch an embodiment.

In an embodiment, if guest module 124A determines that the change instate in the web browsing session should be persisted, then the guestmodule 124A causes state data that describes this change in state to bepersistently stored. FIG. 4 depicts this as action 410 embodied as arequest to persistently store the state data sent from guest module 124Ato host module 114. While, as described above, embodiments maypersistently store data using a variety of different mechanisms, theembodiment of FIG. 4 stores state data persistently at host 110 withinstate data storage 130. When host module 114 receives instruction 410from guest module 124A, host module 114 stores the state data withinstate data storage 130 as shown in action 420. This act of host module114 storing the state data within state data storage 130 need not beautomatic, but instead, may be based upon consultation with policy data.For example, policies may be defined to determine whether state datashould be persisted at all, whether the state data should be persistedusing state data storage 130 or host web browser 112, etc.

The purpose of virtual machine 120A providing host 110 state data topersistently store is to ensure that the necessary information isavailable to notify components of the virtualized web browser of anyrelevant activity (or changes in state) that occur in other componentsof the virtualized web browser. Therefore, after persistently storingrelevant state data concerning the activities of the web browsingsession occurring in each virtual machine, embodiments send out (or“inject”) relevant information to virtual machines as necessary so theVM web browsers executing therein have all the necessary information toprovide a seamless user experience.

Injecting state data into a virtual machine is illustrated in FIG. 4 inaction 430. As shown by action 430, host module 114 is providing guestmodule 124B in virtual machine 120B state data. The state data providedto virtual machine 120B identifies information about how the userpreviously interacted with the virtualized web browser that will be usedby VM web browser 122B in retrieving and/or rendering any content.

Note that not all state data for a user need be injected into eachvirtual machine. For security reasons, it is desirable to only exposethe minimum amount of state data to a virtual machine necessary for theVM web browser executing therein to retrieve and render a requested webpage properly. By “properly,” what is meant is that the requested webpage looks and behaves as the user expects based on his or her pasthistory interacting with web site. Said differently, a properly renderedweb page takes into account all pertinent state data necessary toresolve the display all content therein. Policies defined by the policydata, therefore, will inject into a virtual machine only the state datewhich is deemed pertinent to the assigned responsibilities for thatvirtual machine.

To provide a concrete example, assume that virtual machine 120B istasked with the responsibility of interacting with social media websites. Further assume that policies defined within the policy dataconsider such social media web sites as posing a risk of infection ofmalicious code. Therefore, it would not be advisable to expose anymalicious code that is inadvertently introduced into virtual machine120B to any cookies associated with the user's sensitive information,such as bank account information, passwords, and the like. Consequently,in an embodiment, when host module 114 injects state data into a virtualmachine, host module consults policy data, either stored within host 110or within a virtual machine that is persistently stored, to identifystate data that is pertinent to the assigned responsibilities of thevirtual machine, so that only pertinent state data is injected therein.

Injecting state data into a virtual machine may also be performed towarm up a cache within the virtual machine. For example, if a userpreviously visited a particular web site, cache files for the web sitemay be persistently stored. If the user visits that web site again and anew virtual machine is instantiated to handle the navigation, the cachefiles associated with the particular web site may be injected into thenewly instantiated virtual machine.

When the state information associated with a virtual machine is to bepersisted beyond the lifetime of the virtual machine (as per host module114), it is convenient to persist this information with an identifierrelated to the activity being executed in the virtual machine. Forexample, the top-level domain name (TLD) of the URL being renderedinside the virtual machine may be a convenient identifier. Theidentifier allows this information to be retrieved when it is needed,such as when this information is injected into a virtual machine createdto render a URL with the same TLD as of the virtual machine beingdestroyed.

Policy Based Decision Making

In embodiments of the invention, the operation of host module 114 andguest modules 124A, 124B, . . . 124N is based, at least in part, uponpolicies defined in policy data. For example, host module 114 mayconsult one or more policies defined in policy data to (a) identifywhich virtual machine should be tasked with the responsibility ofservicing a request to retrieve a web page, and/or (b) determine how toinstruct a guest module, within the virtual machine designatedresponsible, to retrieve the web page. Policies may consider a host offactors in determining which virtual machine should service a request toretrieve a web page. For example, the web address, knowledge of anyscripts executing on the parent web page, and whether the requested webpage is in a new or existing web domain may all play a factor indetermining which virtual machines retrieves the requested web page.

When host module 114 receives a subsequent request to display anotherweb page, host module 114 determines, based on policy data accessible tohost module 114, whether the same virtual machine that handled theretrieving and rendering of a previous requested web page shouldretrieve and render the newly requested web page. For example, thepolicy data may indicate that a newly requested web page hascharacteristics similar to a previous web page retrieved and rendered byvirtual machine 120A. In such as case, host module 114 may task guestmodule 124A with retrieving and rendering the newly requested web page.In this way, the policy data may treat web pages within the same webpage similarly so that all the web pages of a particular domain areserviced within the same virtual machine.

Alternately, the policy data may indicate that the newly requested webpage can be processed within the same virtual machine but using a newweb browser. In such a case, host module 114 may task guest module 124Bwith retrieving and rendering the newly requested web page using a newlyinstantiated web browser in virtual machine 120A other than VM webbrowser 122A.

Alternately, the policy data may indicate that the newly requested webpage should be processed within a different virtual machine than anycurrently instantiated. In such a case, host module 114 may instantiatea new virtual machine and instruct a guest module, executing within thenewly instantiated virtual machine, to retrieve and render the newlyrequested web page.

Deallocating Virtual Machines in a Controlled Manner

In an embodiment, when a particular virtual machine is no longerrequired, that virtual machine may be de-allocated. As a result, whenhost module 114 receives notification that the user is closing thevirtualized web browser, host module 114 may, without humanintervention, de-instantiate any virtual machine associated with the webbrowsing session. Thus, any virtual machine that assisted in providingcontent to the virtualized web browser will be automaticallyde-instantiated in an embodiment as a result of the user closing thevirtualized web browser.

Retrieving Content from Different Domains

A virtualized web browser of an embodiment will have the same visuallyappearance and support the same features as a traditional web browser.Therefore, like traditional web browsers, a virtualized web browser willsupport the use of tabs in an embodiment. However, a virtualized webbrowser may retrieve content to be displayed in a tab in a more securemanner than prior approaches.

In an embodiment, upon the virtualized web browser being instructed todisplay a new tab, the virtualized web browser displays the new tabwithout instantiating a new virtual machine. Thus, if a user were torepeated press “Control-T” or a similar mechanism to launch a new tab,the new tab may be created and displayed by the virtualized web browserwithout instantiating or assigning any virtual machines to retrievecontent for the new tab. This advantageously minimizes memory usage ofthe virtualized web browser.

Once a user instructs the virtualized web browser to display a web pagewithin a tab, host module 114 may consult policy data to determinewhether the requested web page may be retrieved and rendered in anexisting virtual machine or if a new virtual machine should beinstantiated.

In an embodiment, requested web pages from the same domain may beretrieved and rendered within the same virtual machine. In this way, thesynchronization of certain resources, such as cache files, is simplifiedand/or expedited. Thus, if a user requests a web page from a domain inwhich another web page has already been fetched and rendered within anexisting virtual machine, then the newly requested web page may befetched and rendered within that same virtual machine. On the otherhand, if the user requests a web page from a domain from which no webpages have previously been fetched, for example, then a new virtualmachine may be instantiated in which to fetch and render that web page.

Synchronizing History Data

Embodiments of the invention seamlessly synchronize resources of avirtualized web browser, and in particular history data, across host 110and virtual machines 120A, 120B, . . . 120N to present a completelynative browser experience to the end user. History data is a type ofstate data. History data is data that describes a user's navigationhistory. History data may include the navigation history of the currentsession as well as web sites and resources previously visited duringprior browsing sessions. By synchronizing history data across thevirtualized web browser, the user is able to perform any type ofoperation involving history data in the same manner as in a traditionalweb browser even though web pages may be retrieved from a plurality ofvirtual machines.

In an embodiment, history data may include bookmarks for the user.History may also include one or more URLs visited by the user as well astitles of web pages and names of resources used. In order to performcertain operations on a web browser, such as back page and forward page,it is necessary to know the sequence and identity of visited web pagesin each tab; therefore, in an embodiment, history data may also identifyone or more actions that were performed with respect to a particular tabof the virtualized web browser.

Operations involving these types of resources will be performedseamlessly since any history data pertinent to the function of thevarious virtual machines will be merged correctly by host module 114.When new history data is created locally within a particular virtualmachine, host module 114 is informed of the new state data so that itmay be persistently stored and injected into other virtual machines asnecessary. For example, if guest module 124A detects that new historydata has been created within virtual machine 120A, then guest module124A may notify host module 114 of the new history data. This may beaccomplished in a variety of different ways by embodiments, e.g., guestmodule 124A may send host module 114 the new history data via a securecommunication channel or guest module 124A may cause the new historydata to be persistently stored and may notify host module 114 that newhistory data has been stored and may be retrieved as needed. In anembodiment, host module 114 causes any new history data sent from avirtual machine to be persistently stored so that host module 114 mayinject the new history data, as needed, into appropriate virtualmachines.

In an embodiment, we optionally do not update history data to identifyall actions taken in a virtual machine. For example, if there is aredirect operation performed in a VM web browser, only the final or thefirst URL may be shared with the host and other VMs, rather than allURLs involved in the redirect.

In an embodiment, history data is used to update the visual appearanceof host web browser. For example, back or forward buttons may bedisplayed as disabled (or “grayed out”) or active depending upon theavailable of appropriate history data to service such operations. When auser initiates the display of a menu in the host operating system thatenables the user to navigate previously visited sites, history data willbe used to perform the operation. For example, if the user performs aright click operation with his or her mouse to display a menu offeringnavigation options, or if the user clicks a back or forward button onthe virtualized web browser, such navigation commands will be performedusing history data obtained from the virtual machines on the system.

Synchronizing Cookies

Embodiments of the invention seamlessly synchronize resources of avirtualized web browser, and in particular cookie data, across host 110and virtual machines 120A, 120B, . . . 120N to present a completelynative browser experience to the end user. Cookie data is a type ofstate data. Cookie data is data that describes a user's cookies. Cookiedata may include cookies dropped in the current session as well ascookies dropping in prior browsing sessions. By synchronizing cookiedata across the virtualized web browser, the user is able to perform anytype of operation involving cookie data in the same manner as in atraditional web browser even though web pages may be retrieved from aplurality of virtual machines.

In an embodiment, when host module 114 instructs a guest module tocoordinate with a VM web browser to retrieve and render a requested webpage, host module 114 provides the guest module cookie data. The cookiedata identifies one or more cookies deemed to be pertinent to theretrieval of the web page. Rather than relying solely using a pushmodel, certain embodiments may also employ a pull model where the guestmodule may send a request to host module 114 to ascertain whether thereare any additional cookies for the user associated with an embedded webpage comprised within the web page. In this way, host module 114 mayprovide to a guest module any cookie data which host module 114 deemspertinent to the retrieval of a requested web page. However, uponretrieving the requested web page, if the guest module determines thatpossession of one or more cookies would affect how the requested webpage is rendered, then the guest module may communicate with host module114 to determine if such cookies have been established for the user, andif so, then the guest module may obtain them from host module 114.

The type and amount of cookie data sent from host module 114 to a guestmodule may be configured using policies defined in the policy data. Forexample, in an embodiment, host module 114, based on consultation withpolicy data, may only send to a guest module cookie data that identifiescookies associated with the top-level domain of the requested web pageand does not identify any cookies associated with the domain of anyembedded web pages comprised within the requested web page. On the otherhand, in other embodiment, policy data may define a different set ofpolicies, and host module 114 in that embodiment may provide, to a guestmodule, cookie data that identifies cookies associated with thetop-level domain of the requested web page and any domain of anyembedded web pages comprised within the requested web page. Embodimentsmay employ policy data that defines a variety of policies for specifyingwhich cookies should be provided to a virtual machine.

Embodiments of the invention may store cookie data using a variety ofdifferent mechanisms. Cookie data may be stored in any location and inany manner that state data may be stored. Cookie data may be stored atstate data storage 130 in an embodiment. In another embodiment, cookiedata may be persistently stored by host web browser 112. In anotherembodiment, cookie data may be stored in a virtual machine that ispersistently stored.

A guest module may employ a variety of mechanisms to determine when a VMweb browser drops a cookie. For example, the guest module may detect theperformance of set cookie operation via an API, a callback, or a plug-into the VM web browser.

In an embodiment, a guest module may redirect processing of any setcookie instruction or get cookie instruction comprised within the webpage to host module 114. In this way, host module 114 may become acentral manager of all cookies throughout the virtualized web browser,regardless of which particular virtual machine is retrieving a web page.

Managing Display Issues

Embodiments of the invention enable a web page retrieved and renderedwithin a virtual machine by a VM web browser to be displayed upon aphysical display device by host web browser 112 executing on host 110.Host module 114 assists in assembling the rendered content obtained fromthe host or from any virtual machine responsible in contributingrendered content for a web page displayed by host web browser 114.

Certain types of web content may be deemed secure while other types ofweb content may be deemed insecure. For example, web sites accessibleover a secure connection (vis-à-vis a https connection) or web pageshosted internally on an Intranet may be deemed secure (i.e., low risk ofcomprising malicious software). Other public web sites available on theInternet may be deemed insecure due to the higher level risk that suchsites may be infected with malicious code.

Embodiments may treat secure web sites different than insecure websites. A virtualized web browser of an embodiment may interact with asecure web site using a VM web browser executing with a virtual machinehaving characteristics specifically tailored to interact with the secureweb site. In the same vein, a virtualized web browser of an embodimentmay interact with an insecure web site using a VM web browser executingwith a virtual machine having characteristics specifically tailored tointeract with the insecure web site.

A single web page may contain secure portions and insecure portions. Forexample, a child web page may be embedded within a parent web page usinga HTML construct such as an “iFrame.” The parent web page may be deemedsecure while the child web page may be deemed insure. In an embodiment,when a requested web page contains both secure and insecure content, awarning may be displayed to the user. The warning may inform the userthat the requested web page contains content deemed insecure. Thewarning may allow the user to consent to assume the risk and continuewith processing the web page. If the user wishes to proceed withretrieving the web page, then a new virtual machine may be instantiatedfor purposes of retrieving the insecure portions of the requested webpage. The newly instantiated virtual machine will contain a guest moduleand a VM web browser. The newly instantiated guest module and VM webbrowser will cooperate to retrieve and render the insecure portions ofthe requested web page. Once host module 114 obtains screen data for theinsecure and secure portions of the requested web page, host module 114may assemble the rendered portions of the requested web page andinstruct host web browser 112 to display the assembled web page.

Host module 114 may obtain screen data for a rendered portion of a webpage in a variety of different ways. For example, in an embodiment, hostmodule 114 may obtain screen data by accessing a frame buffer thatstores data representing a rendered portion of a web page. Host module114 may do so for each virtual machine responsible for rendering aportion of a requested web page. After obtaining all the pieces of therequested web page, host module 114 may assemble the pieces and instructhost web browser 112 to display the assembled web page.

Host module 114 may obtain screen data for a rendered portion of a webpage in a variety of different ways. For example, in an embodiment, hostmodule 114 may obtain screen data may accessing a frame buffer thatstores data representing a rendered portion of a web page. Host module114 may do so for each virtual machine responsible for rendering aportion of a requested web page. After obtaining all the pieces of therequested web page, host module 114 may assemble the pieces and instructhost web browser 112 to display the assembled web page.

In another embodiment, host module 114 may obtain screen data using anoperating system protocol for displaying the contents of one frame inanother frame. In this way, the rendered content displayed by a VM webbrowser may be identified and displayed by host web browser 112.

Note that it may be desirable in certain embodiments to configure apolicy to disallow the display of certain types of content. For example,content originating from certain prohibited web sites or possessingcertain undesirable characteristics, such as embedded graphics or textassociated with one or more keywords, may be prevented from beingdisplayed. In such an embodiment, policy data may be stored whichdefines one or more polices that demarcate when certain content shouldor should not be displayed by host web browser 112. When host module 114obtains screen data, host module 114 may consult the policy data todetermine whether it is permissible to display the screen data. If it isnot permissible to display a set of screen data, then host module 114instructs host web browser 112 to display any portion of the web pagewhich is allowed, but redacts any disallowed portions of the requestedweb page by causing such portions to be displayed blank or with agraphic that explains that the portion is not being displayed forviolation of a policy.

In an embodiment, when the virtualized web browser comprises two or moretabs, each tab may be serviced by a separate VM web browser executingwithin a separate virtual machine.

Managing Downloading and Uploading Files Using a Virtualized Web Browser

Embodiments of the invention provide for a virtualized web browser thatsupports the same user experience as a traditional web browser. However,unlike traditional web browsers, a virtualized web browser retrieves andrenders content within virtual machines which need not be persisted. Asa result, how a virtualized web browser supports uploading anddownloading files is substantially different than how a traditional webbrowser supports such functions.

In an embodiment, when the virtualized web browser receives aninstruction to download one or more files external to and not anintegrated part of the web page (such as when a file is downloaded froma web site), the virtualized web browser displays an interface whichenables at least a portion of a file system, maintained by host 110, tobe browsed while preventing files stored within a virtual machine to bebrowsed.

For example, with reference to FIG. 1, assume that host web browser 112receives an instruction to download one or more files from a web page.Host web browser 112 in turn displays an interface (such as a pop updialogue box) which enables at least a portion of a file system,maintained by host 110, to be browsed while preventing files storedwithin any of virtual machines 120A, 120B, . . . 120N to be browsed.

Once host web browser 112 receives input that identifies a targetlocation within the file system maintained by host 110, host web browser112 instructs a VM web browser to download the one or more files to thetarget location. Note that in certain embodiments, not all of the filesystem maintained by host 110 is exposed to the user. In such anembodiment, host module 114 may consult policy data to determine whichportions of the file system maintained by host 110 be visible andexposed to the user. Such an embodiment may be used to protect certainfiles from being tampered with by the user or to hide certain areas ofthe file system from the user.

In an embodiment, policy data may define a policy that specifies thatany files downloaded from outside of a particular region (such as thephysical machine itself, the Intranet, one or more specified domainsdeemed to be trusted, etc.) are deemed untrustworthy. When host module114 exposes an interface to a virtual machine that facilitates thedownload of files to a target location, host module 114 may consultpolicy data to determine how to treat the download files. If, as aresult of consulting policy data, host module 114 determines that thedownloaded files should be deemed untrustworthy, then host module 114allows the files to be downloaded to the target location, butadditionally stores data that identifies the one or more downloadedfiles to be untrusted documents. The download files may be subsequentlyprocessed differently (such as being opened only in a virtual machinedesigned to handle untrusted documents) by virtue of being labeleduntrusted documents.

The policy data consulted by host module 114 may require that hostmodule 114 store a record in a log file to document any files beingdownloaded. In this way, the virtualized web browser will produce arecord of all the files it downloads. This log file may be configured tocontain a variety of other supporting metadata, such as the userdownloading the file, the day and time of the download, etc.

In an embodiment, prior to storing a copy of the downloaded file to thetarget location, a copy of the downloaded file may be stored in anintermediate location. To help illustrate this principle, the followingdescription will reference FIG. 5, which is an illustration ofdownloading a file to an intermediate location according to anembodiment of the invention. FIG. 5 will be used to describe how a filemay be downloaded using VM web browser 122A executing in virtual machine120A to a particular location in file system 540 on host 110.

In an embodiment, policy data will instruct where a downloaded file willinitially reside. Different embodiments may employ different approachesfor intaking downloaded files. In an embodiment, guest module 124Aconsults policy data to determine where a file downloaded by VM webbrowser 122A should be stored. The policy data may indicate that thedownloaded file should be stored at temporary location 510. Temporarylocation 510 may be designed to only store data downloaded from virtualmachine 120A or may store data from any virtual machine in system 100.

The purpose of storing a downloaded file in temporary location 510 is toallow analysis on the downloaded file prior to moving the downloadedfile to its final destination. Analysis that may be performed on adownloaded file at temporary location 510 includes but is not limited tochecking for malicious code, such as a virus. The purpose of runningsuch analysis is to determine if the downloaded file should be deemedsafe. Temporarily location 510 may, but need not, be located within avirtual machine.

In an embodiment, after a downloaded file is deemed safe as a result ofanalysis performed on the downloaded file at temporary location 510, thedownloaded file may be transferred to shared location 520. Alternately,a downloaded file may immediately be stored at shared location 520instead of temporary location 510. In such an embodiment, the analysisthat was discussed above as being performed at temporary location 510may instead be performed at shared location 520, or not performed atall.

Shared location 520 is a location where downloaded files may be storedand accessed by other components within system 100. For example, in anembodiment, a downloaded file is never moved or copied to file system540. Instead, a downloaded file is copied into shared location 520. Ashadow file that links to the downloaded file in shared location 520 isstored at the target location in file system 540. A user browsing to thelocation in file system 540 where he or she wanted to store a copy ofthe downloaded file would instead see the shadow file. The user may notbe able to ascertain that the shadow file is not the downloaded file.The shadow file may be moved or copied into any location. If anoperation is to be performed on the shadow file (for example, the userclicks on the shadow file to open up the file), the link between theshadow file and the download file will be traversed and the operationwill be performed against the downloaded link within shared location 520(for example, clicking on the shadow file within file system 540 willcause the downloaded file within shared location 520 to open in avirtual machine). The advantage of this embodiment is that if thedownloaded file contains malicious code that is undetected, themalicious code will remain outside of host 110, thereby minimizing orpreventing infection. In another embodiment, if a downloaded file isdeemed safe within shared location 520, then it may be moved to thetarget location within file system 540.

Shared location 520 may be implemented within a virtual machine.Alternately, downloaded files may be stored directly into a virtualmachine, such as virtual machine 530 in FIG. 5. As shown in FIG. 5, adownloaded file may be stored directly into virtual machine 530 by VMweb browser 122A or the downloaded file may be transferred from eithertemporary location 510 or shared location 520. Virtual machine 530 isintended to represent a secure repository for downloaded files. In anembodiment, a new virtual machine 530 may be instantiated for eachdownloaded file to provide a pristine environment in which analysis maybe performed to determine whether the downloaded file contains anymalicious code. In an embodiment, if a downloaded file is deemed safewithin virtual machine 530, then it may be moved to the target locationwithin file system 540.

Note that embodiments need not implement all of temporary location 510,shared location 520, and virtual machine 530, as embodiments mayimplement zero or more of these features. The discussion of thesecomponents is meant to illustrate the variety of design choicesembodiments of the invention enjoy in implementing a quarantined areafor downloaded files to facilitate the performance of analysis upon thedownloaded files.

Embodiments may move a downloaded file to host 110 using a variety ofdifferent approaches. Policy data may specify a particular mechanism touse in moving a downloaded file into file system 540 based on the sizeof the downloaded file. For example, based on the size of the downloadedfile, it may be more efficient to move the downloaded file into filesystem 540 by way of a network connection, by way of copying to disk, orby way of copying into memory.

Embodiments also support uploading files. FIG. 6 is an illustration ofuploading a file according to an embodiment of the invention. In anembodiment, a user may instruct host web browser 112 to upload one ormore files. Host web browser 112 will communicate this instruction tohost module 114. When host module 114 receives an instruction to uploadone or more files stored locally to an external target location, hostmodule 114 displays an interface which enables at least a portion of afile system, maintained by host 110, to be browsed while preventingfiles stored within any virtual machine to be browsed. When host module114 receives input identifying one or more files in the file system,host module 114 moves the selected files to shared location 610.

Guest module 124C is instructed by host module 114 to upload theselected files in shared location 610. Therefore, guest module 124Ccommunicates with VM web browser 122C to cause VM web browser 122C toupload the selected files from shared location 610 to the targetlocation. Advantageously, only the particular files to be uploaded areexposed to virtual machine 120C, as the remainder of the files in filesystem 620 remain inaccessible to virtual machine 120C. If any maliciouscode were to reside within a virtual machine such as virtual machine120C, the malicious code would be prevented from inspecting the fileswithin file system 620 or obtaining any data therein.

Policy data consulted by host module 114 may require that host module114 store a record in a log file to document any files being uploaded.In this way, the virtualized web browser will produce a record of allfiles uploaded using the virtualized web browser. This log file may beconfigured to contain a variety of other supporting metadata, such asthe user uploading the file, the day and time of the upload, where thefile(s) were uploaded, etc.

Extensions

Note that embodiments of the invention have been chiefly described withreference to a virtualized web browser. However, the principlespresented herein are equally application to other types of applications.Indeed, the teachings described above are equally applicable to any typeof virtualized application, such as a virtualized email client orvirtualized email server. In such an embodiment, rather than retrievingand rendering web pages within virtual machines, each virtual machinemay retrieve and render email or email attachments. Host 110 may beimplemented on a cell phone, tablet PC, and the like, and virtualmachines 120A, 120B, . . . 120N may reside in a data center or otherremote location. When a user instructs the cell phone or tablet PC todisplay an email or an email attachment, the request could be routed toa particular virtual machine, which retrieves the email, renders theemail or email attachment to produce screen data, and sends the screendata to the cell phone or tablet PC for display.

Hardware Mechanisms

In an embodiment, host 110 and one or more of virtual machines 120A,120B, . . . 120N of FIG. 1 may be implemented on a computer system. FIG.7 is a block diagram that illustrates a computer system 700 upon whichan embodiment of the invention may be implemented. In an embodiment,computer system 700 includes processor 704, main memory 706, ROM 708,storage device 710, and communication interface 718. Computer system 700includes at least one processor 704 for processing information. Computersystem 700 also includes a main memory 706, such as a random accessmemory (RAM) or other dynamic storage device, for storing informationand instructions to be executed by processor 704. Main memory 706 alsomay be used for storing temporary variables or other intermediateinformation during execution of instructions to be executed by processor704. Computer system 700 further includes a read only memory (ROM) 708or other static storage device for storing static information andinstructions for processor 704. A storage device 710, such as a magneticdisk or optical disk, is provided for storing information andinstructions.

Computer system 700 may be coupled to a display 712, such as a cathoderay tube (CRT), a LCD monitor, and a television set, for displayinginformation to a user. An input device 714, including alphanumeric andother keys, is coupled to computer system 700 for communicatinginformation and command selections to processor 704. Other non-limiting,illustrative examples of input device 714 include a mouse, a trackball,or cursor direction keys for communicating direction information andcommand selections to processor 704 and for controlling cursor movementon display 712. While only one input device 714 is depicted in FIG. 7,embodiments of the invention may include any number of input devices 714coupled to computer system 700.

Embodiments of the invention are related to the use of computer system700 for implementing the techniques described herein. According to oneembodiment of the invention, those techniques are performed by computersystem 700 in response to processor 704 executing one or more sequencesof one or more instructions contained in main memory 706. Suchinstructions may be read into main memory 706 from anothermachine-readable medium, such as storage device 710. Execution of thesequences of instructions contained in main memory 706 causes processor704 to perform the process steps described herein. In alternativeembodiments, hard-wired circuitry may be used in place of or incombination with software instructions to implement embodiments of theinvention. Thus, embodiments of the invention are not limited to anyspecific combination of hardware circuitry and software.

The term “machine-readable storage medium” as used herein refers to anytangible medium that participates in storing instructions which may beprovided to processor 704 for execution. Such a medium may take manyforms, including but not limited to, non-volatile media and volatilemedia. Non-volatile media includes, for example, optical or magneticdisks, such as storage device 710. Volatile media includes dynamicmemory, such as main memory 706.

Non-limiting, illustrative examples of machine-readable media include,for example, a floppy disk, a flexible disk, hard disk, magnetic tape,or any other magnetic medium, a CD-ROM, any other optical medium, a RAM,a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, orany other medium from which a computer can read.

Various forms of machine readable media may be involved in carrying oneor more sequences of one or more instructions to processor 704 forexecution. For example, the instructions may initially be carried on amagnetic disk of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over anetwork link 720 to computer system 700.

Communication interface 718 provides a two-way data communicationcoupling to a network link 720 that is connected to a local network. Forexample, communication interface 718 may be an integrated servicesdigital network (ISDN) card or a modem to provide a data communicationconnection to a corresponding type of telephone line. As anotherexample, communication interface 718 may be a local area network (LAN)card to provide a data communication connection to a compatible LAN.Wireless links may also be implemented. In any such implementation,communication interface 718 sends and receives electrical,electromagnetic or optical signals that carry digital data streamsrepresenting various types of information.

Network link 720 typically provides data communication through one ormore networks to other data devices. For example, network link 720 mayprovide a connection through a local network to a host computer or todata equipment operated by an Internet Service Provider (ISP).

Computer system 700 can send messages and receive data, includingprogram code, through the network(s), network link 720 and communicationinterface 718. For example, a server might transmit a requested code foran application program through the Internet, a local ISP, a localnetwork, subsequently to communication interface 718. The received codemay be executed by processor 704 as it is received, and/or stored instorage device 710, or other non-volatile storage for later execution.

In the foregoing specification, embodiments of the invention have beendescribed with reference to numerous specific details that may vary fromimplementation to implementation. Thus, the sole and exclusive indicatorof what is the invention, and is intended by the applicants to be theinvention, is the set of claims that issue from this application, in thespecific form in which such claims issue, including any subsequentcorrection. Any definitions expressly set forth herein for termscontained in such claims shall govern the meaning of such terms as usedin the claims. Hence, no limitation, element, property, feature,advantage or attribute that is not expressly recited in a claim shouldlimit the scope of such claim in any way. The specification and drawingsare, accordingly, to be regarded in an illustrative rather than arestrictive sense.

What is claimed is:
 1. One or more non-transitory computer-readable storage mediums storing one or more sequences of instructions for synchronizing history data across a virtualized web browser, which when executed by one or more processors, cause: upon a user instructing a virtualized web browser, executing on a host operating system, to display a web page, a host module executing on the host operating system instantiating one or more virtual machines and determining a composition of history data for said user to be injected into each of said one or more virtual machines based on a policy, wherein said policy specifies what types of history data should be transferred into each of said one or more virtual machines for said user without receiving a request from said one or more virtual machines to do so, and wherein each of said one or more virtual machines comprises a guest module; after a first virtual machine and a second virtual machine, of said one or more virtual machines, has been instantiated, the host module (a) instructing a first guest module executing within the first virtual machine to retrieve at least a first portion of the web page and (b) instructing a second guest module executing within the second virtual machine, of said one or more virtual machines, to retrieve at least a second portion of the web page; upon the host module receiving rendered screen data content from at least the first guest module and the second guest module, the host module instructing the virtualized web browser to display the web page using the rendered screen data content received from at least the first guest module and the second guest module; after the second guest module determines that a set of history data created by web browsing activity performed within said second virtual machine should be persisted, the second guest module sending a request to the host module to persistently store said set of history data; and upon the host module determining, in consultation with said policy, the first virtual machine should retrieve web pages while possessing said set of history data, the host module providing to the first guest module, executing within the first virtual machine, said set of history data without receiving any request from the first guest module to do so, wherein the set of history data describes said web browsing activity performed by said user within said second virtual machine.
 2. The one or more non-transitory computer readable mediums of claim 1, wherein the host module, upon receiving the set of history data, persistently stores the set of history data within a file server or a database.
 3. The one or more non-transitory computer readable mediums of claim 1, wherein the history data describes one or more bookmarks of the user.
 4. The one or more non-transitory computer readable mediums of claim 1, wherein the history data describes one or more URLs that were visited by the user.
 5. The one or more non-transitory computer readable mediums of claim 1, wherein the history data describes one or more titles of web pages.
 6. The one or more non-transitory computer readable mediums of claim 1, wherein the history data identifies one or more actions that were performed with respect to a particular tab of the virtualized web browser.
 7. The one or more non-transitory computer readable mediums of claim 1, wherein execution of the one or more sequences of instructions further causes: the first guest module issuing a second request to the host module to determine if the first virtual machine may retrieve a requested web page.
 8. The one or more non-transitory computer readable mediums of claim 7, wherein execution of the one or more sequences of instructions further causes: the host module consulting policy data that identifies one or more policies to determine how to respond to the second request from the first guest module.
 9. The one or more non-transitory computer readable mediums of claim 1, wherein execution of the one or more sequences of instructions further causes: a web browser, executing within the first virtual machine, performing a back navigation operation or a forward navigation operation based on the set of history data received from the host module.
 10. The one or more non-transitory computer readable mediums of claim 1, wherein execution of the one or more sequences of instructions further causes: a web browser, executing within the first virtual machine, displaying a set of links to visited web pages using the history data, wherein the visited web pages includes a set of web pages which the web browser did not retrieve.
 11. The one or more non-transitory computer readable mediums of claim 1, wherein execution of the one or more sequences of instructions further causes: updating the visual appearance of navigation controls of the virtualized web browser based on the availability of history data to service operations associated with the navigation controls.
 12. An apparatus configured to synchronize history data across a virtualized web browser, comprising: one or more processors; and one or more computer-readable mediums storing one or more sequences of instructions, which when executed by the one or more processors, cause: upon a user instructing a virtualized web browser, executing on a host operating system, to display a web page, a host module executing on the host operating system instantiating one or more virtual machines and determining a composition of history data for said user to be injected into each of said one or more virtual machines based on a policy, wherein said policy specifies what types of history data should be transferred into each of said one or more virtual machines for said user without receiving a request from said one or more virtual machines to do so, and wherein each of said one or more virtual machines comprises a guest module; after a first virtual machine and a second virtual machine, of said one or more virtual machines, has been instantiated, the host module (a) instructing a first guest module executing within the first virtual machine to retrieve at least a first portion of the web page, and (b) instructing a second guest module executing within the second virtual machines, of said one or more virtual machines, to retrieve at least a second portion of the web page; upon the host module receiving rendered screen data content from at least the first guest module and the second guest module, the host module instructing the virtualized web browser to display the web page using the rendered screen data content received from at least the first guest module and the second guest module; after the second guest module determines that a set of history data created by web browsing activity performed within said second virtual machine should be persisted, the second guest module sending a request to the host module to persistently store said set of history data; and upon the host module determining, in consultation with said policy, the first virtual machine should retrieve web pages while possessing said set of history data, the host module providing to the first guest module, executing within the first virtual machine, said set of history data without receiving a request from the first guest module to do so, wherein the set of history data describes said web browsing activity performed by said user within said second virtual machine.
 13. The apparatus of claim 12, wherein execution of the one or more sequences of instructions further causes: a web browser, executing within the particular virtual machine, performing a back navigation operation or a forward navigation operation based on the history data received from the host module.
 14. The apparatus of claim 12, wherein execution of the one or more sequences of instructions further causes: a web browser, executing within the particular virtual machine, displaying a set of links to visited web pages using the history data, wherein the visited web pages includes a set of web pages which the web browser did not retrieve.
 15. The apparatus of claim 12, wherein execution of the one or more sequences of instructions further causes: updating the visual appearance of navigation controls of the virtualized web browser based on the availability of history data to service operations associated with the navigation controls.
 16. A method for synchronizing history data across a virtualized web browser, comprising: upon a virtualized web browser, executing on a host operating system, receiving an instruction to display a web page, a host module, executing on the host operating system, instantiating one or more virtual machines and determining a composition of history data for said user to be injected into each of said one or more virtual machines based on a policy, wherein said policy specifies what types of history data should be transferred into each of said one or more virtual machines for said user without receiving a request from said one or more virtual machines to do so, and wherein each of said one or more virtual machines comprises a guest module; after a first virtual machine, of said one or more virtual machines, has been instantiated, the host module (a) instructing a first guest module executing within the first virtual machine to retrieve at least of first portion of the web page, and (b) instructing a second guest module executing within a second virtual machine, of said one or more virtual machines, to retrieve at least a second portion of the web page; upon the host module receiving rendered screen data content from at least the first guest module and the second guest module, the host module instructing the virtualized web browser to display the web page using the rendered screen data content received from at least the first guest module and the second guest module; after the second guest module determines that a set of history data created by web browsing activity performed within said second virtual machine should be persisted, the second guest module sending a request to the host module to persistently store said set of history data; and upon the host module determining, in consultation with said policy, the first virtual machine should retrieve web pages while possessing said set of history data, the host module providing to the first guest module, executing within the first virtual machine, said set of history data without receiving a request from the first guest module to do so, wherein the set of history data describes said web browsing activity performed by said user within said second virtual machine. 